Configuration For Beam Failure Recovery

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A base station may indicate one or more resources for beam failure recovery. The one or more resources may comprise one or more resources for downlink transmission and one or more resources for uplink transmission. A beam failure recovery may be based on the one or more resources for downlink transmission. A wireless device may send, based on the one or more resources for uplink transmission, uplink information for beam failure recovery.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/694,197, filed Mar. 14, 2022, which is a continuation of U.S.application Ser. No. 17/157,352, filed Jan. 25, 2021, now U.S. Pat. No.11,310,859, which is a continuation of U.S. application Ser. No.16/370,476, filed Mar. 29, 2019, now U.S. Pat. No. 10,904,940, whichclaims the benefit of U.S. Provisional Application No. 62/650,725, filedMar. 30, 2018. The above-referenced applications are hereby incorporatedby reference in their entireties.

BACKGROUND

A wireless device may be configured to receive transmissions via one ofmultiple different beams associated with a cell. Although thiscapability may increase cell capacity, individual beams may be subjectto interruption, interference, transmission irregularities at a cell,and/or other issues. If such problems occur and a wireless device cannotbe reconfigured to receive transmissions via a different beam, servicemay be degraded. It is desired to improve wireless communications byincreasing the likelihood for a successful beam failure recoveryprocedure, without adversely increasing signaling overhead and/ordecreasing spectral efficiency.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for wirelesscommunications. A base station may send configuration information for abeam failure recovery (BFR) procedure. A base station and/or a wirelessdevice may have different capabilities for beam correspondence. Theconfiguration information may comprise a transmission beam index. Awireless device may determine, based on the transmission beam index, oneor more transmission beams of the wireless devices for the BFRprocedure. The wireless device may select, based on a measurement of oneor more downlink signals, one or more candidate beams of the basestation. The wireless device may send, to the base station, one or moreuplink signals to indicate the one or more candidate beams of the basestation. The one or more uplink signals may be sent via the one or moretransmission beams of the wireless device. The BFR procedure may be usedwith or without beam correspondence.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A and FIG. 16B show examples of a downlink beam failure event.

FIG. 17 shows an example of a downlink beam failure recovery (BFR)procedure.

FIG. 18 shows an example of a scheduling request procedure.

FIG. 19 shows an example of a physical uplink control channel (PUCCH)configuration for a BFR procedure.

FIG. 20 shows an example of configuring a PUCCH configuration for a BFRprocedure.

FIG. 21 shows an example of a PUCCH configuration for a BFR procedure.

FIG. 22 shows an example PUCCH configuration procedure.

FIG. 23 shows an example beam index mapping procedure.

FIG. 24 shows an example beam index mapping procedure.

FIG. 25 shows an example of a beam selection for a BFR procedure.

FIG. 26 shows an example of performing a BFR procedure.

FIG. 27 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto wireless communication systems in multicarrier communication systems.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

-   -   3GPP 3rd Generation Partnership Project    -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ARQ Automatic Repeat Request    -   AS Access Stratum    -   ASIC Application-Specific Integrated Circuit    -   BA Bandwidth Adaptation    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   BPSK Binary Phase Shift Keying    -   BWP Bandwidth Part    -   CA Carrier Aggregation    -   CC Component Carrier    -   CCCH Common Control CHannel    -   CDMA Code Division Multiple Access    -   CN Core Network    -   CP Cyclic Prefix    -   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex    -   C-RNTI Cell-Radio Network Temporary Identifier    -   CS Configured Scheduling    -   CSI Channel State Information    -   CSI-RS Channel State Information-Reference Signal    -   CQI Channel Quality Indicator    -   CSS Common Search Space    -   CU Central Unit    -   DC Dual Connectivity    -   DCCH Dedicated Control Channel    -   DCI Downlink Control Information    -   DL Downlink    -   DL-SCH Downlink Shared CHannel    -   DM-RS DeModulation Reference Signal    -   DRB Data Radio Bearer    -   DRX Discontinuous Reception    -   DTCH Dedicated Traffic Channel    -   DU Distributed Unit    -   EPC Evolved Packet Core    -   E-UTRA Evolved UMTS Terrestrial Radio Access    -   E-UTRAN Evolved-Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplex    -   FPGA Field Programmable Gate Arrays    -   F1-C F1-Control plane    -   F1-U F1-User plane    -   gNB next generation Node B    -   HARQ Hybrid Automatic Repeat reQuest    -   HDL Hardware Description Languages    -   IE Information Element    -   IP Internet Protocol    -   LCID Logical Channel Identifier    -   LTE Long Term Evolution    -   MAC Media Access Control    -   MCG Master Cell Group    -   MCS Modulation and Coding Scheme    -   MeNB Master evolved Node B    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MN Master Node    -   NACK Negative Acknowledgement    -   NAS Non-Access Stratum    -   NG CP Next Generation Control Plane    -   NGC Next Generation Core    -   NG-C NG-Control plane    -   ng-eNB next generation evolved Node B    -   NG-U NG-User plane    -   NR New Radio    -   NR MAC New Radio MAC    -   NR PDCP New Radio PDCP    -   NR PHY New Radio PHYsical    -   NR RLC New Radio RLC    -   NR RRC New Radio RRC    -   NSSAI Network Slice Selection Assistance Information    -   O&M Operation and Maintenance    -   OFDM Orthogonal Frequency Division Multiplexing    -   PBCH Physical Broadcast CHannel    -   PCC Primary Component Carrier    -   PCCH Paging Control CHannel    -   PCell Primary Cell    -   PCH Paging CHannel    -   PDCCH Physical Downlink Control CHannel    -   PDCP Packet Data Convergence Protocol    -   PDSCH Physical Downlink Shared CHannel    -   PDU Protocol Data Unit    -   PHICH Physical HARQ Indicator CHannel    -   PHY PHYsical    -   PLMN Public Land Mobile Network    -   PMI Precoding Matrix Indicator    -   PRACH Physical Random Access CHannel    -   PRB Physical Resource Block    -   PSCell Primary Secondary Cell    -   PSS Primary Synchronization Signal    -   pTAG primary Timing Advance Group    -   PT-RS Phase Tracking Reference Signal    -   PUCCH Physical Uplink Control CHannel    -   PUSCH Physical Uplink Shared CHannel    -   QAM Quadrature Amplitude Modulation    -   QFI Quality of Service Indicator    -   QoS Quality of Service    -   QPSK Quadrature Phase Shift Keying    -   RA Random Access    -   RACH Random Access CHannel    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RA-RNTI Random Access-Radio Network Temporary Identifier    -   RB Resource Blocks    -   RBG Resource Block Groups    -   RI Rank indicator    -   RLC Radio Link Control    -   RRC Radio Resource Control    -   RS Reference Signal    -   RSRP Reference Signal Received Power    -   SCC Secondary Component Carrier    -   SCell Secondary Cell    -   SCG Secondary Cell Group    -   SC-FDMA Single Carrier-Frequency Division Multiple Access    -   SDAP Service Data Adaptation Protocol    -   SDU Service Data Unit    -   SeNB Secondary evolved Node B    -   SFN System Frame Number    -   S-GW Serving GateWay    -   SI System Information    -   SIB System Information Block    -   SMF Session Management Function    -   SN Secondary Node    -   SpCell Special Cell    -   SRB Signaling Radio Bearer    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   sTAG secondary Timing Advance Group    -   TA Timing Advance    -   TAG Timing Advance Group    -   TAI Tracking Area Identifier    -   TAT Time Alignment Timer    -   TB Transport Block    -   TC-RNTI Temporary Cell-Radio Network Temporary Identifier    -   TDD Time Division Duplex    -   TDMA Time Division Multiple Access    -   TTI Transmission Time Interval    -   UCI Uplink Control Information    -   UE User Equipment    -   UL Uplink    -   UL-SCH Uplink Shared CHannel    -   UPF User Plane Function    -   UPGW User Plane Gateway    -   VHDL VHSIC Hardware Description Language    -   Xn-C Xn-Control plane    -   Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme, for example, depending on transmission requirements and/or radioconditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Media Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MA CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs indicating one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or uncasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterInformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signaling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6 , FIG. 7A, FIG. 7B,FIG. 8 , and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel. A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for acarrier. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6 , asubframe may be divided into two equally sized slots 603 with 0.5 msduration. For example, 10 subframes may be available for downlinktransmission and 10 subframes may be available for uplink transmissionsin a 10 ms interval. Other subframe durations such as, for example, 0.5ms, 1 ms, 2 ms, and 5 ms may be supported. Uplink and downlinktransmissions may be separated in the frequency domain. Slot(s) mayinclude a plurality of OFDM symbols 604. The number of OFDM symbols 604in a slot 605 may depend on the cyclic prefix length. A slot may be 14OFDM symbols for the same subcarrier spacing of up to 480 kHz withnormal CP. A slot may be 12 OFDM symbols for the same subcarrier spacingof 60 kHz with extended CP. A slot may comprise downlink, uplink, and/ora downlink part and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a preemption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a wireless device is configured with a secondary carrier on a primarycell, the wireless device may be configured with an initial BWP forrandom access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base statin may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided a default DL BWP, a default BWP may be an initialactive DL BWP.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. shows an example of three BWPs configured, BWP1 (1010and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040)may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be deactivated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery procedure and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery procedure, and/or a contentionresolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery procedure associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery procedure, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery procedure. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For a beamfailure recovery procedure, the base station may configure the wirelessdevice with a different time window (e.g., bfr-ResponseWindow) tomonitor response to on a beam failure recovery request. The wirelessdevice may start a time window (e.g., ra-ResponseWindow orbfr-ResponseWindow) at a start of a first PDCCH occasion, for example,after a fixed duration of one or more symbols from an end of a preambletransmission. If the wireless device sends (e.g., transmits) multiplepreambles, the wireless device may start a time window at a start of afirst PDCCH occasion after a fixed duration of one or more symbols froman end of a first preamble transmission. The wireless device may monitora PDCCH of a cell for at least one random access response identified bya RA-RNTI, or for at least one response to a beam failure recoveryrequest identified by a C-RNTI, at a time that a timer for a time windowis running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4 stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more radio technologies (e.g., an NR system, etc.).The one or more radio technologies may comprise at least one of:multiple technologies related to a physical layer; multiple technologiesrelated to a MAC layer; and/or multiple technologies related to an RRClayer Enhancement of the one or more radio technologies may improveperformance of a wireless network Enhancement of the one or more radiotechnologies may also increase a system throughput or a data rate of atransmission Enhancement of the one or more radio technologies mayreduce battery consumption of a wireless device Enhancement of the oneor more radio technologies may improve latency of a data transmissionbetween a base station and a wireless device Enhancement of the one ormore radio technologies may improve a network coverage of a wirelessnetwork. Enhancement of the one or more radio technologies may improvetransmission efficiency of a wireless network.

A base station (e.g., a gNB) and/or a wireless device may have multipleantennas, for example, to support a transmission with high data rate(such as in an NR system). A wireless device may perform one or morebeam management procedures, as shown in FIG. 9B, for example, ifconfigured with multiple antennas.

A wireless device may perform a downlink beam management based on one ormore CSI-RSs and/or one or more SS blocks. In a beam managementprocedure, a wireless device may measure a channel quality of a beampair link. The beam pair link may comprise a transmitting beam from abase station and a receiving beam at the wireless device. A wirelessdevice may measure the multiple beam pair links between the base stationand the wireless device, for example, if the wireless device isconfigured with multiple beams associated with multiple CSI-RSs and/orSS blocks.

A wireless device may send (e.g., transmit) one or more beam managementreports to a base station. The wireless device may indicate one or morebeam pair quality parameters, for example, in a beam management report.The one or more beam pair quality parameters may comprise at least oneor more beam identifications; RSRP; and/or PMI, CQI, and/or RI of atleast a subset of configured multiple beams.

A base station and/or a wireless device may perform a downlink beammanagement procedure on one or multiple Transmission and Receiving Point(TRPs), such as shown in FIG. 9B. Based on a wireless device's beammanagement report, a base station may send (e.g., transmit), to thewireless device, a signal indicating that a new beam pair link is aserving beam. The base station may transmit PDCCH and/or PDSCH to thewireless device using the serving beam.

A wireless device and/or a base station may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery request (BFRQ) procedure, for example, if at least a beamfailure occurs. A beam failure may occur if a quality of beam pairlink(s) of at least one PDCCH falls below a threshold. The threshold maycomprise an RSRP value (e.g., −140 dbm, −110 dbm, or any other value)and/or a Signal to Interference & Noise Ratio (SINR) value (e.g., −3 dB,−1 dB, or any other value), which may be configured in an RRC message.

FIG. 16A shows an example of a first beam failure event. A base station1602 may send (e.g., transmit) a PDCCH from a transmission (Tx) beam toa receiving (Rx) beam of a wireless device 1601 from a TRP. The basestation 1602 and the wireless device 1601 may start a beam failurerecovery procedure on the TRP, for example, if the PDCCH on the beampair link (e.g., between the Tx beam of the base station 1602 and the Rxbeam of the wireless device 1601) have a lower-than-threshold RSRPand/or SINR value due to the beam pair link being blocked (e.g., by amoving vehicle 1603, a building, or any other obstruction).

FIG. 16B shows an example of a second beam failure event. A base station1610 may send (e.g., transmit) a PDCCH from a beam to a wireless device1611 from a first TRP 1614. The base station 1602 and the wirelessdevice 1611 may start a beam failure recovery procedure on a new beam ona second TRP 1612, for example, if the PDCCH on the beam is blocked(e.g., by a moving vehicle, building, or any other obstruction).

A wireless device may measure a quality of beam pair links using one ormore RSs. The one or more RSs may comprise one or more SS blocks and/orone or more CSI-RS resources. A CSI-RS resource may be determined by aCSI-RS resource index (CRI). A quality of beam pair links may beindicated by, for example, an RSRP value, a reference signal receivedquality (e.g., RSRQ) value, and/or a CSI (e.g., SINR) value measured onRS resources. A base station may indicate whether an RS resource, usedfor measuring beam pair link quality, is QCLed (Quasi-Co-Located) withDM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH may beQCLed, for example, if the channel characteristics from a transmissionon an RS to a wireless device, and that from a transmission on a PDCCHto the wireless device, are similar or same under a configuredcriterion. The RS resource and the DM-RSs of the PDCCH may be QCLed, forexample, if Doppler shift and/or Doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are the same.

A wireless device may monitor a PDCCH on M (e.g., 2, 4, 8) beam pairlinks simultaneously, where M≥1 and the value of M may depend at leaston capability of the wireless device. Monitoring a PDCCH may comprisedetecting a DCI via the PDCCH transmitted on common search spaces and/orwireless device specific search spaces. Monitoring multiple beam pairlinks may increase robustness against beam pair link blocking. A basestation may send (e.g., transmit) one or more messages comprisingparameters indicating a wireless device to monitor PDCCH on differentbeam pair link(s) in different OFDM symbols.

A base station may send (e.g., transmit) one or more RRC messages and/orMAC CEs comprising parameters indicating Rx beam setting of a wirelessdevice for monitoring PDCCH on multiple beam pair links. A base stationmay send (e.g., transmit) an indication of a spatial QCL between DL RSantenna port(s) and DL RS antenna port(s) for demodulation of DL controlchannel. The indication may comprise a parameter in a MAC CE, an RRCmessage, a DCI, and/or any combinations of these signaling.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of DL data channel, for example, forreception of data packet on a PDSCH. A base station may send (e.g.,transmit) DCI comprising parameters indicating the RS antenna port(s)are QCLed with DM-RS antenna port(s).

A wireless device may measure a beam pair link quality based on CSI-RSsQCLed with DM-RS for PDCCH, for example, if a base station sends (e.g.,transmits) a signal indicating QCL parameters between CSI-RS and DM-RSfor PDCCH. The wireless device may start a BFR procedure, for example,if multiple contiguous beam failures occur.

A wireless device may send (e.g., transmit) a BFR signal (e.g., a BFRQsignal) on an uplink physical channel to a base station, for example, ifstarting a BFR procedure. The base station may send (e.g., transmit) aDCI via a PDCCH in a CORESET, for example, after or in response toreceiving the BFR signal (e.g., the BFRQ signal) on the uplink physicalchannel. The wireless device may determine that the BFR procedure issuccessfully completed, for example, after or in response to receivingthe DCI via the PDCCH in the CORESET.

A base station may send (e.g., transmit) one or more messages comprisingconfiguration parameters of an uplink physical channel, or signal, fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH (e.g.,BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., BFR-PUCCH); and/or acontention-based PRACH resource (e.g., CF-PRACH). Combinations of thesecandidate signals and/or channels may be configured by the base station.A wireless device may autonomously select a first resource fortransmitting a BFR signal (e.g., a BFRQ signal), for example, if thewireless device is configured with multiple resources for the BFR signal(e.g., the BFRQ signal). The wireless device may select a BFR-PRACHresource for transmitting a BFR signal (e.g., a BFRQ signal), forexample, if the wireless device is configured with the BFR-PRACHresource, a BFR-PUCCH resource, and/or a CF-PRACH resource. The basestation may send (e.g., transmit) a message to the wireless deviceindicating a resource for transmitting the BFR signal (e.g., the BFRQsignal), for example, if the wireless device is configured with aBFR-PRACH resource, a BFR-PUCCH resource, and/or a CF-PRACH resource.

A base station may send (e.g., transmit) a response to a wirelessdevice, for example, after receiving one or more BFR signals (e.g., oneor more BFRQ signals). The response may comprise the CRI associated withthe candidate beam that the wireless device may indicate in the one ormultiple BFR signals (e.g., the one or multiple BFRQ signals).

Wireless communications may be associated with various services and/orcapabilities, such as beam forming capabilities, beam correspondencecapabilities, beam failure recovery capabilities, and/or othercommunication capabilities (e.g., a transmission beam filter and areceiving beam filter of a wireless device may not be tuned for beamcorrespondence). Some wireless communications (e.g., a RACH-based BFRprocedure) may cause some problems and/or inefficiencies, for example,based on different capabilities and/or other information. A wirelessdevice and/or a base station may not be able to determine a transmissionbeam for transmitting uplink data for a BFR, for example, if beamcorrespondence is not supported by the wireless device and/or by thebase station. Different services and/or capabilities may cause anunsuccessful BFR procedure, for example, if the wireless device and/orthe base station is(are) not able to determine a transmission beam,other resources, and/or other information. An occurrence of anunsuccessful BFR procedure, a failure in determining a transmission beamand/or other problems may result in an increase of power consumption, anincrease of a time delay, and/or a decrease of spectrum efficiency.

A base station and a wireless device may perform a PUCCH-based BFRprocedure with or without beam correspondence. A base station mayconfigure one or more PUCCH resources dedicated for a BFR. The one ormore PUCCH resources may comprise one or more parameters (e.g., beamindexes, RS indexes) associated with one or more transmission beams of awireless device. A base station may set a predefined value for atransmission beam index, for example, for beam correspondence. Thetransmission beam index may be comprised in the one or more PUCCHresources dedicated for a BFR. A wireless device may select a candidatebeam of the base station for a BFR. The wireless device may determine(e.g., select) a transmission beam of the wireless device thatcorresponds to the selected candidate beam of the base station, forexample, if the transmission beam index is set to the predefined valuefor beam correspondence. The transmission beam index may be setdifferently for different beam non-correspondence configurations.Advantages may be achieved by providing a unified solution for atransmission beam selection for both beam correspondence and beamnon-correspondence.

A base station may configure a BFR PUCCH resource set comprising aplurality of BFR PUCCH resources. A wireless device may receive one ormore messages comprising the BFR PUCCH resource set. The wireless devicemay select one or more BFR PUCCH resources based on determining one ormore candidate beams of the base station (e.g., for a downlinkcommunication). Each of the BFR PUCCH resources may be associated with adifferent RS. The base station may send, to the wireless device and viathe candidate beams, the different RSs. By selecting a BFR PUCCHresource associated with a first RS, the wireless device may implicitlyselect a first candidate beam, of the base station, associated with thefirst RS. Each BFR PUCCH resource may comprise a transmission beam indexindicating a transmission beam of a wireless device. The transmissionbeam index may be an RS index that indicates a second RS associated witha transmission beam (e.g., a transmission beam corresponding to areceiving beam on which the wireless device receives the second RS sentfrom the base station, or a transmission beam corresponding to atransmission beam on which the wireless device transmits an SRS to thebase station). The wireless device may retrieve a value of atransmission beam index comprised in the selected BFR PUCCH resource.The wireless device may select, based on the value indicated by thetransmission beam index, a transmission beam, of the wireless device,for sending an uplink signal (e.g., PUCCH signal) for a BFR. The secondRS indicated by the transmission beam index may be the same to the firstRS for beam correspondence or may be different from the first RS forbeam non-correspondence. The wireless device may select, based on thesecond RS, the transmission beam for an uplink transmission for a BFRwhile implicitly selecting, by selecting a BFR PUCCH resource, thecandidate beam of the base station associated with the first RS. Byconfiguring different transmission beam index values for each BFR PUCCHresource, the wireless device may flexibly select one or moretransmission beams of the wireless devices and one or more candidatebeams of the base station. The base station and the wireless device mayperform a robust BFR procedure with or without beam correspondence.

Advantages may be achieved by configuring a plurality of BFR PUCCHresources. The wireless device may implicitly indicate, to the basestation, a selection of a candidate beam without adding an additionaldata field, for example, if different RSs of the base station areassociated with different BFR PUCCH resources. Transmission beam indexesof the plurality of BFR PUCCH resources may provide flexibility for thewireless device to select one or more transmission beams of the wirelessdevice (e.g., other than the active transmission beam of the wirelessdevice) for an uplink transmission for a BFR while independentlyselecting one or more candidate beams of the base station.

A base station may configure a (e.g., single) BFR PUCCH resource. TheBFR PUCCH resource may comprise a transmission beam index indicating atransmission beam of a wireless device. The transmission beam index maybe an RS index that indicates a value of an RS associated with atransmission beam (e.g., a transmission beam corresponding to areceiving beam that receives the second RS sent from the base station,or a transmission beam corresponding to a transmission beam on which thewireless device transmits an SRS to the base station). The wirelessdevice may receive one or more messages comprising the BFR PUCCHresource and may select a candidate beam of the base station (e.g., fora downlink communication). The wireless device may generate an uplinksignal for a BFR to indicate the selection of the candidate beam. Theuplink signal may comprise a beam indicator indicating the selectedcandidate beam of the base station. The selected candidate beam may beassociated with a first RS. The wireless device may retrieve a value ofa transmission beam index comprised in the BFR PUCCH resource. Thewireless device may select, based on the value indicated by thetransmission beam index, the transmission beam, of the wireless device,for sending the uplink signal (e.g., a PUCCH signal) for a BFR. Thevalue of a transmission beam index may indicate a second RS. The secondRS may be the same to the first RS for beam correspondence or may bedifferent from the first RS for beam non-correspondence. The wirelessdevice may select, based on the second RS, the transmission beam for anuplink transmission for a BFR. The wireless device may perform a robustBFR procedure with or without beam correspondence, for example, byindependently selecting the candidate beam of the base station and thetransmission beam of the wireless device.

Advantages may be achieved by configuring a BFR PUCCH resource and/or anuplink signal comprising a beam indicator. The wireless device mayindependently select, based on a transmission beam index of the BFRPUCCH resource, a transmission beam of the wireless device and mayindicate, via the beam indicator, a selection of a candidate beam. Atransmission beam index of the BFR PUCCH resource may enable thewireless device to select a candidate transmission beam of the wirelessdevice (e.g., other than the active transmission beam of the wirelessdevice) for an uplink transmission for a BFR. A mapping relationshipbetween a value of the beam indicator and an RS index of a set of RSresources configured for the wireless device may reduce a signalingoverhead by reducing the size of the beam indicator.

A base station may send (e.g., transmit) a DCI via a PDCCH. The DCI maybe used for at least one of: a scheduling assignment/grant; a slotformat notification; a pre-emption indication; and/or a power-controlcommand. The DCI may comprise at least one of: an identifier of a DCIformat; downlink scheduling assignment(s); uplink scheduling grant(s); aslot format indicator; a pre-emption indication; power-controlcommand(s) for PUCCH and/or PUSCH; and/or a power-control command for anSRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format; a PDSCH resourceindication; a transport format; HARQ information; control informationrelated to multiple antenna schemes; and/or a command for a powercontrol of the PUCCH. An uplink scheduling grant DCI may compriseparameters indicating at least one of: an identifier of a DCI format; aPUSCH resource indication; a transport format; HARQ-related information;and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCImessage sizes. Supporting multiple beams and/or spatial multiplexing ina spatial domain and noncontiguous allocation of RBs in a frequencydomain may require a larger scheduling message, in comparison with anuplink grant allowing for a frequency-contiguous allocation. DCIs may becategorized into different DCI formats. A particular DCI format may havea certain message size and/or usage.

A wireless device may monitor one or more PDCCHs for detecting one ormore DCIs with one or more DCI formats. The wireless device may monitorthe PDCCH in a common search space and/or in a wireless device-specificsearch space. A wireless device may monitor a PDCCH with a limited setof DCI formats, for example, to save power and/or reduce powerconsumption. The wireless device may consume more power, for example, ifthe wireless device attempts to detect more types of DCI formats.

Information in the DCI formats used for a downlink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; an RB allocation; a time resource allocation; a bandwidthpart indicator; a HARQ process number; one or more MCSs; one or moreNDIs; one or more RVs; MIMO-related information; a downlink assignmentindex (DAI); a TPC for a PUCCH; an SRS request; and/or a padding ifnecessary. The MIMO-related information may comprise at least one of: aPMI; precoding information; a transport block swap flag; a power offsetbetween a PDSCH and a reference signal; a reference-signal scramblingsequence; a number of layers; and/or one or more antenna ports for thetransmission; and/or a Transmission Configuration Indication (TCI).Information in the DCI formats used for an uplink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; a bandwidth part indication; a resource allocation type; anRB allocation; a time resource allocation; an MCS; an NDI; Phaserotation of the uplink DMRS; precoding information; a CSI request; anSRS request; an Uplink index/DAI; a TPC for a PUSCH; and/or a padding ifnecessary.

A base station may perform a CRC scrambling for a DCI, for example,before transmitting the DCI via a PDCCH. The base station may perform aCRC scrambling by binarily adding multiple bits of at least one wirelessdevice identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, SP CSI C-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, etc.)on the CRC bits of the DCI. The wireless device may check the CRC bitsof the DCI, for example, if the wireless device attempts to detect theDCI. The wireless device may receive the DCI, for example, if the CRC isscrambled by a sequence of bits that is the same as the at least onewireless device identifier.

To support a wide bandwidth operation, a base station may send (e.g.,transmit) one or more PDCCHs in different control resource sets(coresets). A base station may send (e.g., transmit) one or more RRCmessages comprising configuration parameters of one or more coresets. Acoreset may comprise at least one of: a first OFDM symbol; a number ofconsecutive OFDM symbols; a set of resource blocks; and/or a CCE-to-REGmapping. A base station may send (e.g., transmit) a PDCCH in a dedicatedcoreset for a particular purpose, for example, for a beam failurerecovery confirmation. A wireless device may monitor a PDCCH fordetecting a DCI in one or more configured coresets, to reduce the powerconsumption.

A base station (e.g., a gNB) and/or a wireless device may perform one ormore beam management procedure, for example, if the base station and/orthe wireless device are configured with multiple beams (e.g., in asystem such as an NR system). The wireless device may perform a BFRprocedure, for example, if one or more beam pair links between the basestation and the wireless device fail.

FIG. 17 shows an example of a BFR procedure. The BFR procedure may befor a primary cell or a secondary cell. At step 1701, a wireless devicemay receive one or more messages (e.g., RRC messages) comprising BFRparameters (e.g., BFRQ parameters). At step 1702, the wireless devicemay detect at least one beam failure according to at least one of BFRparameters, for example, the BFR parameters received at step 1701. Thewireless device may start a first timer, for example, after or inresponse to detecting the at least one beam failure. At step 1703, thewireless device may select a candidate beam (e.g., based on a receivedpower of downlink reference signal such as SSB, CSI-RS, and/or DMRS),for example, after or in response to detecting the at least one beamfailure. The selected beam may be a beam with a good channel quality(e.g., based on RSRP, SINR, and/or Block Error Rate (BLER)) from a setof candidate beams. The candidate beams may be identified by a set ofreference signals (e.g., SSBs, or CSI-RSs). At step 1704, the wirelessdevice may send (e.g., transmit) a BFR signal (e.g., at least a firstBFR signal) to a base station, for example, after or in response to theselecting the candidate beam. The BFR signal may be associated with theselected beam. The wireless device may send (e.g., transmit) the BFRsignal with a transmission beam corresponding to a receiving beamassociated with the selected beam. The BFR signal may comprise apreamble transmitted via a PRACH resource, an SR signal transmitted viaa PUCCH resource, a beam failure recovery signal transmitted via a PUCCHresource, and/or a beam report transmitted via a PUCCH and/or PUSCHresource. The wireless device may start a response window, for example,after or in response to sending (e.g., transmitting) the BFR signal. Theresponse window may be determined by a timer using a value configured(or determined) by the base station. At step 1705, the wireless devicemay monitor a PDCCH in a first coreset, for example, if the responsewindow is running (e.g., the response window is not expired). The firstcoreset may be associated with the BFR procedure. The wireless devicemay monitor the PDCCH in the first coreset, for example, in condition ofsending (e.g., transmitting) the BFR signal. At step 1706, the wirelessdevice may receive a DCI (e.g., a first DCI) via the PDCCH in the firstcoreset, for example, during the response window. At step 1707, thewireless device may determine that the BFR procedure is successfullycompleted, for example, if the wireless device receives the DCI via thePDCCH in the first coreset before the response window expires. Thewireless device may stop the first timer, for example, after or inresponse to the BFR procedure successfully being completed. The wirelessdevice may stop the response window, for example, after or in responseto the BFR procedure successfully being completed.

The wireless device may increment a transmission count (e.g., anunsuccessful transmission count), for example, if the wireless does notreceive the DCI during the response window. The transmission count maybe initialized to a first number (e.g., 0), for example, before the BFRprocedure is triggered. At step 1708, the wireless device may repeat oneor more actions (e.g., steps of FIG. 17 ), for example, if thetransmission count is less than a configured maximum transmissionnumber. The one or more actions may comprise at least one of: a BFRsignal transmission (e.g., at step 1704); starting the response window;monitoring for the PDCCH (e.g., at step 1705); incrementing thetransmission count, for example, if no response is received during theresponse window. At step 1709, the wireless device may determine thatthe BFR procedure is unsuccessfully completed, for example, if thetransmission count is equal to or greater than the configured maximumtransmission number.

A wireless device may trigger an SR for requesting a UL-SCH resource,for example, if the wireless device has data for a new transmission. Abase station may send (e.g., transmit) to a wireless device at least onemessage comprising parameters indicating zero SR configuration orindicating one or more SR configurations. An SR configuration maycomprise a set of PUCCH resources for an SR on one or more BWPs and/orone or more cells. On a BWP, at most one PUCCH resource for an SR may beconfigured. Each SR configuration may correspond to one or more logicalchannels. Each logical channel may be mapped to zero or one SRconfiguration configured by the at least one message. An SRconfiguration of a logical channel (LCH) that triggers a buffer statusreport (BSR) may be considered as a corresponding SR configuration for atriggered SR.

The at least one message may further comprise (e.g., for each SRconfiguration) one or more parameters indicating at least one of: an SRprohibit timer; a maximum number of an SR transmission; a parameterindicating a periodicity and offset of an SR transmission; and/or aPUCCH resource. The SR prohibit timer may be a duration during which thewireless device is not allowed to transmit the SR. The maximum number ofSR transmission may be a number of allowed SR transmissions for thewireless device.

A PUCCH resource may be indicated by at least: a frequency location(e.g., a starting PRB); and/or a PUCCH format associated with an initialcyclic shift of a base sequence and a time domain location (e.g., astarting symbol index). A PUCCH format may be PUCCH format 0, PUCCHformat 1, PUCCH format 2, PUCCH format 3, or PUCCH format 4, or anyother format. The PUCCH format 0 may occupy 1 or 2 OFDM symbols and mayhave a size (e.g., a payload size) less than or equal to 2 bits. ThePUCCH format 1 may occupy a number of symbols (e.g., 4, 5, . . . , or 14OFDM symbols) and may have a size (e.g., a payload size) less than orequal to 2 bits. The PUCCH format 2 may occupy 1 or 2 OFDM symbols andmay have a size (e.g., a payload size) greater than 2 bits. The PUCCHformat 3 may occupy a number of symbols (e.g., 4, 5, . . . , or 14 OFDMsymbols) and may have a size (e.g., a payload size) greater than 2 bits.The PUCCH format 4 may occupy a number of symbols (e.g., 4, 5, . . . ,or 14 OFDM symbols) and may have a size (e.g., a payload size) greaterthan 2 bits.

A PUCCH format for an SR transmission may be the PUCCH format 0 or thePUCCH format 1. A wireless device may send (e.g., transmit) a PUCCHsignal via a PUCCH resource for a corresponding SR configuration, forexample, if the wireless device sends (e.g., transmits) a positive SR.The wireless device may not send the PUCCH signal via the PUCCH resourcefor the corresponding SR configuration, for example, if the wirelessdevice does not send a positive SR. A wireless device may send (e.g.,transmit) a PUCCH by setting the cyclic shift to a first value (e.g.,0), for example, for a positive SR transmission using the PUCCH format0. A wireless device may send (e.g., transmit) a PUCCH by setting afirst bit (e.g., before BPSK modulated on a sequence) to a first value(e.g., 0), for example, for a positive SR transmission using the PUCCHformat 1.

An SR may be multiplexed with a HARQ-ACK or CSI, for example, on a PUCCHformat. A wireless device may determine a cyclic shift of the basesequence based on the initial cyclic shift. The wireless device maydetermine a first cyclic shift based on one or more values of one ormore HARQ-ACK bits, for example, if a positive SR is multiplexed withHARQ-ACK. The wireless device may determine a second cyclic shift basedon one or more value of the one or more HARQ-ACK bits, for example, if anegative SR is multiplexed with HARQ-ACK. The first cyclic shift may bedifferent from the second cyclic shift.

A wireless device may maintain an SR transmission counter (e.g.,SR_COUNTER) associated with an SR configuration. A wireless device mayset the SR_COUNTER of the SR configuration to a first value (e.g., 0),for example, if an SR of the SR configuration is triggered, and thereare no other pending SRs corresponding to the same SR configuration.

A wireless device may determine that an SR is pending until it iscancelled, for example, if the SR is triggered. All pending SR(s) may becancelled, for example, if one or more UL grants accommodate all pendingdata available for a transmission.

A wireless device may determine one or more PUCCH resources on an activeBWP as valid PUCCH resources, for example, at an SR transmissionoccasion. A wireless device may send (e.g., transmit) a PUCCH in a PUCCHresource associated with an SR configuration, for example, if thewireless device sends (e.g., transmits) a positive SR. A wireless devicemay send (e.g., transmit) the PUCCH, for example, using the PUCCH format0 or the PUCCH format 1, according to the PUCCH configuration.

FIG. 18 shows an example of an SR procedure. At step 1801, a wirelessdevice may receive one or more messages (e.g., an RRC message)comprising parameters of one or more SR configurations. The parametersmay indicate (e.g., for each of the one or more SR configurations) atleast one of: an SR prohibit timer; a maximum number of an SRtransmission; a parameter indicating a periodicity and offset of an SRtransmission; and/or a PUCCH resource. At step 1802, a wireless devicemay set a counter (e.g., SR_COUNTER) to a first value (e.g., 0), forexample, if an SR of a SR configuration is triggered and pending (e.g.,after or in response to a BSR being triggered on a LCH corresponding tothe SR configuration) and/or if there is no other pending SRscorresponding to the SR configuration.

A step 1803, a wireless device may determine whether there is at leastone valid PUCCH resource for the pending SR. The wireless device mayinitiate a random access procedure on a PCell, for example, if there isno valid PUCCH resource for the pending SR. The wireless device maycancel the pending SR. At step 1803.5, the wireless device may initiatea random access procedure and/or cancel the pending SR, for example, ifthere is no valid PUCCH resource for the pending SR.

A wireless device may determine an SR transmission occasion on the atleast one valid PUCCH resource based on the periodicity and the offsetof an SR transmission, for example, if there is at least one valid PUCCHresource for the pending SR. At step 1804, the wireless device may waitfor another SR transmission occasion, for example, if the SR prohibittimer is running. As step 1806, the wireless device may increment theSR_COUNTER by one, instruct the physical layer of the wireless device tosend (e.g., signal, transmit, etc.) the SR on the at least one validPUCCH resource for the SR, for example, if the SR prohibit timer is notrunning and the SR_COUNTER is less than the maximum number of an SRtransmission (at step 1805). The physical layer of the wireless devicemay send (e.g., transmit) a PUCCH on the at least one valid PUCCHresource for the SR. The wireless device may monitor a PDCCH fordetecting one or more DCIs for one or more uplink grants, for example,after or in response to transmitting the PUCCH. At step 1807, thewireless device may receive the one or more UL grants.

At step 1808, the wireless device may determine whether the wirelessdevice has received sufficient UL grant(s) (e.g., sufficient number ofUL grants, UL grant(s) granting sufficient amount of uplink resourcesfor all pending data, etc.). At step 1809, the wireless device maycancel the pending SR and/or stop the SR prohibit timer, for example, ifthe wireless device receives one or more uplink grants which mayaccommodate all pending data available for a transmission.

At step 1808, the wireless device may repeat one or more actions (e.g.,one or more steps of FIG. 18 ), for example, if the wireless device doesnot receive one or more uplink grants which may accommodate all pendingdata available for transmission. The one or more actions may comprise atleast one of: determining the at least one valid PUCCH resource (e.g.,at step 1803); checking whether the SR prohibit timer is running (e.g.,at step 1804); whether the SR_COUNTER is equal or greater than themaximum number of an SR transmission (e.g., at step 1805); incrementingthe SR_COUNTER (e.g., at step 1806), transmitting the SR and startingthe SR prohibit timer (e.g., at step 1806); and/or monitoring for aPDCCH to receive one or more uplink grant(s) (e.g., at step 1807).

At step 1810, a wireless device may release PUCCH(s) for one or moreserving cells, may release SRS(s) for the one or more serving cells, mayclear one or more configured downlink assignments and uplink grants, mayinitiate a random access procedure (e.g., on a PCell), and/or may cancelthe pending SR, for example, if the SR_COUNTER indicates a number equalto or greater than the maximum number of an SR transmission.

A base station and/or a wireless device may perform a PRACH-based BFRprocedure, for example, if at least one beam failure instance isidentified and/or if a beam correspondence exists between the basestation and the wireless device. A beam correspondence may exist, forexample, if a wireless device is configured to send (e.g., transmit) anuplink signal using a transmission beam corresponding to a receivingbeam for receiving a downlink signal from a base station. The wirelessdevice may determine the corresponding transmission beam by using RFand/or digital beamforming parameters corresponding to those beamformingparameters for the corresponding receiving beam, for example, if thewireless device identifies the receiving beam by determining RF and/ordigital beamforming parameters for receiving downlink signals from thebase station. The beamforming parameters for the correspondingtransmission beam (e.g., one or more transmission beam parameterscomprising spatial filter(s) to determine a beam direction) may be thesame as the beamforming parameters for the corresponding receiving beamfor the beam correspondence case. Beam correspondence existence maysimplify a transceiver design. Using beam correspondence, a wirelessdevice may determine a transmission beam based on a receiving beam.Using beam correspondence, a base station may not indicate thetransmission beam (e.g., thereby reducing the signaling overhead)because the wireless device may determine a transmission beam based oninformation of the corresponding receiving beam. Using beamcorrespondence, a wireless device may avoid an uplink beam sweeping forhelping a base station find a proper uplink beam (e.g., thereby reducingthe power consumption of the wireless device). Beam correspondence mayexist, for example, in a TDD configuration case, if the transmission andreception of the wireless device share the same set of physical antennaelements, and/or if the transmission and reception of the wirelessdevice have a same or similar beam width.

A beam correspondence may not exist, for example, if a physical antennafor a transmission is separated from a physical antenna for a receptionand/or the beam width for the transmission and reception is different. Awireless device may not be able to determine a transmission beam basedon a receiving beam for receiving downlink signals. A base station mayexplicitly indicate a transmission beam of a PUCCH and/or PUSCHtransmission (e.g., by an RRC message, a MAC CE, or a DCI), for example,if the wireless device is not able to determine a transmission beambased on a receiving beam. A base station and a wireless device may notperform a PRACH-based BFR procedure, for example, if at least one beamfailure instance is identified and if a beam correspondence does notexist. A wireless device may perform a PRACH-based BFR procedure and maydetermine, for a PRACH preamble transmission, a transmission beamassociated with the receiving beam for receiving a signal on a candidatebeam, for example, if a beam correspondence does not exist. The basestation may not be able to detect the PRACH preamble (e.g., because thebase station may not expect that there is any uplink transmission on thetransmission beam on which the wireless device transmits the PRACHpreamble), for example, due to no beam correspondence between thetransmission beam and the receiving beam in the base station and/or thewireless device. The PRACH-based BFR procedure may result inunsuccessful beam failure recovery, which may further lead to a radiolink failure, for example, if there is no beam correspondence betweenthe transmission beam and the receiving beam. A beam failure recoveryprocedure may be improved by designing a PUCCH-based BFR procedure,which may be applicable regardless of the existence of a beamcorrespondence.

A base station may send (e.g., transmit), to a wireless device, at leastone message comprising parameters indicating an RS index, for example,for a normal PUCCH transmission of one or more uplink control data(e.g., an SR transmission, a HARQ-ACK feedback, a CSI report). The RSindex may be an SSB resource index, a CSI-RS resource index, and/or anSRS resource index. The SSB resource index comprise one of a set of SSBresource indexes associated to one or more serving beams. The CSI-RSresource index may comprise one of a set of CSI-RS resource indexesassociated with one or more serving beams. A serving beam may be a beamvia which the base station sends (e.g., transmits) PDCCH and/or PDSCH tothe wireless device. The wireless device may determine a transmissionbeam based on the RS index explicitly indicated by the base station fora PUCCH transmission. The RS index may be further activated by a MAC CE.The wireless device may determine a transmission beam for the PUCCHtransmission as same as a transmission beam for the last PRACHtransmission in a random access procedure, for example, before receivingthe MAC CE. The wireless device may determine, based on the RS indexindicated by the MAC CE, the transmission beam for the PUCCHtransmission, for example, after receiving the MAC CE. The determinationof the transmission beam may be referred to as a spatial domaintransmission filter determination.

A base station and a wireless device may perform a PUCCH-based BFRprocedure, for example, if at least one beam failure instance isidentified and if a beam correspondence does not exist. A wirelessdevice may determine a transmission beam for a PUCCH, for example, ifthe PUCCH is used for a BFR procedure. In a PUCCH configuration for anormal PUCCH transmission (e.g., for an SR transmission, a HARQ-ACKfeedback, and/or a CSI report), a transmission beam for the normal PUCCHtransmission may be indicated and/or activated by an RRC message and/ora MAC CE. The transmission beam may be associated with an RS index, forexample, based on the RRC message and/or the MAC CE. The RS index may beone of the serving beams. The wireless device may identify beam failureson all or some serving beams (e.g., indicated by multiple SSB resourceindexes and/or multiple CSI-RS resource indexes), for example, if thewireless device is triggered with a BFR procedure. The wireless devicemay select a candidate beam from a second set of beams, other than thefailing serving beams, with communication quality (e.g., referencesignal received power (RSRP) and/or reference signal received quality(RSRQ)) satisfying (e.g., greater than) a configured threshold (e.g., apower value and/or a quality value). The wireless device may determine aPUCCH resource associated with the candidate beam. The transmission beamfor the PUCCH may not be necessarily one of the serving beams (e.g., allthe serving beams may fail), for example, where the one of the servingbeams for the normal PUCCH transmission is configured and activated bythe RRC message and/or the MAC CE. The base station may not successfullyreceive the PUCCH, for example, if the wireless device uses atransmission beam associated with one of the serving beams which havebeen failed. One or more enhanced PUCCH configurations for a BFRprocedure may reduce beam misalignment for a PUCCH transmission for atriggered BFR procedure. One or more enhanced PUCCH configurations for aBFR procedure may provide a flexible method to indicate a transmissionbeam for a PUCCH transmission for a BFR procedure, for example, for boththe beam correspondence existence and the beam correspondencenon-existence. Based on one or more enhanced PUCCH configurations for aBFR procedure, a base station may receive the PUCCH transmission, forexample, even if all downlink serving beams fail (e.g., at least a beamfailure instance identified).

FIG. 19 shows an example of a physical uplink control channel (PUCCH)configuration for a BFR procedure. A base station 1910 may support aplurality of beams (e.g., beams 1930, 1931, 1932, and 1933) and maychoose at least one serving beam (e.g., the beam 1930). The beams 1931,1932, and 1933 may not be serving beams but may be candidate beams. Abeam may be identified by (or represented by, or associated with) an RSindex. The beam 1930 may be associated with RS 0, the beam 1931 may beassociated with RS 1, the beam 1932 may be associated with RS 2, and thebeam 1933 may be associated with RS 3. The base station 1910 may send(e.g., transmit) at least one message (e.g., an RRC message) comprisingparameters indicating a first set of RSs (e.g., one or more active setof RSs, such as the RS 0 of a serving beam) and indicating a second setof RSs (e.g., one or more candidate set of RSs, such as the RS 1, the RS2, and the RS 3 of candidate beams). The at least one message may besent to the wireless device 1920 via the serving beam 1930. The firstset of RSs may indicate one or more beams (e.g., the beam 1930associated with the RS 0) via which the base station sends (e.g.,transmits) one or more PDCCHs and/or PDSCHs. The second set of RSs mayindicate one or more candidate beams (e.g., the beam 1931 associatedwith the RS 1, the beam 1932 associated with the RS 2, and the beam 1933associated with the RS 3) from which the wireless device may detectand/or determine a candidate beam with quality better than a threshold,for example, if the one or more beams (e.g., the beam 1930) associatedwith the first set of RSs (e.g., RS 0) fail.

The at least one message may comprise parameters indicating a BFR PUCCHresource set 1950 comprising first multiple BFR PUCCH resources andindicating at least one normal PUCCH resource set 1960 comprising one ormore second multiple normal PUCCH resources. The wireless device 1920may determine a PUCCH resource from the BFR PUCCH resource set 1950 tosend (e.g., transmit) a PUCCH signal for a BFR procedure, for example,if the BFR procedure is triggered. The wireless device 1920 maydetermine a PUCCH resource from the normal PUCCH resource set 1960, forexample, if the wireless device 1920 performs an SR transmission (e.g.,by a BSR being triggered), performs a HARQ-ACK transmission, and/orsends a CSI report on a PUCCH.

Each PUCCH resource of the BFR PUCCH resource set 1950 may be associatedwith an RS index of the second set (e.g., candidate set) of RSs (e.g.,the RS 1, the RS 2, and the RS 3). The association between an RS indexof the second set and a PUCCH resource of the BFR PUCCH resource set1950 may be indicated to the wireless device 1920. PUCCH resource 1 ofthe BFR PUCCH resource set 1950 may be associated with the RS1, PUCCHresource 2 of the BFR PUCCH resource set 1950 may be associated with theRS 2, and PUCCH resource 3 of the BFR PUCCH resource set 1950 may byassociated with the RS3. Each PUCCH resource of the BFR PUCCH resourceset 1950 may indicate, to the wireless device 1920, a time resource, afrequency resource, and/or a beam index. A PUCCH resource, of the BFRPUCCH resource set 1950, selected by the wireless device 1920 may bedetermined by the base station 1910 based on the time resource, thefrequency resource, and/or the beam index of the selected PUCCHresource. By receiving a PUCCH mapped on a time resource 1 (T_resource1) and a frequency resource 1 (F_resource 1), the base station 1910 maydetermine that the wireless device 1920 has selected the PUCCH resource1 of the BFR PUCCH resource set 1950. By receiving a PUCCH sent using atransmission beam, of the wireless device, associated with a value ofthe beam index of the PUCCH resource 1, the base station 1910 maydetermine that the wireless device 1920 has selected the PUCCH resource1 of the BFR PUCCH resource set 1950. By receiving a PUCCH mapped on atime resource 2 (T_resource 2) and a frequency resource 2 (F_resource2), the base station 1910 may determine that the wireless device 1920has selected the PUCCH resource 2 of the BFR PUCCH resource set 1950. Byreceiving a PUCCH sent using a transmission beam, of the wirelessdevice, associated with a value of the beam index of the PUCCH resource2, the base station 1910 may determine that the wireless device 1920 hasselected the PUCCH resource 2 of the BFR PUCCH resource set 1950. Byreceiving a PUCCH mapped on a time resource 3 (T_resource 3) and afrequency resource 3 (F_resource 3), the base station 1910 may determinethat the wireless device 1920 has selected the PUCCH resource 3 of theBFR PUCCH resource set 1950. By receiving a PUCCH sent using atransmission beam, of the wireless device 1920, associated with a valueof the beam index of the PUCCH resource 3, the base station 1910 maydetermine that the wireless device 1920 has selected the PUCCH resource3 of the BFR PUCCH resource set 1950. A beam index of a PUCCH resource(e.g., the PUCCH resources 1, 2, or 3) may be an SSB index, a CSI-RSindex, or an SRS index. The beam index of the PUCCH resource may beactivated by the RRC message, not by a MAC CE, and may be different froma beam index of transmission on a normal PUCCH. The beam index of aPUCCH resource (e.g., the PUCCH resources 1, 2, and 3) may be differentfrom the RS index associated with the PUCCH resource. The RS indexassociated with a PUCCH resource (e.g., the PUCCH resources 1, 2, or 3)may indicate a candidate beam which has a receiving signal quality, at areceiver of the wireless device 1920, satisfying (e.g., better than) athreshold. The beam index of a PUCCH resource may be used, at atransmitter of the wireless device 1920, to determine a transmissionbeam for a PUCCH transmission for a BFR.

The beam index of a PUCCH resource (e.g., the PUCCH resources 1, 2, or3) may indicate an RS index that is associated with a transmission beamof the wireless device 1920. The wireless device 1920 may send, to thebase station 1910, a PUCCH for a BFR using a beam 1941, for example, ifthe wireless device 1920 selects a PUCCH resource, of the BFR PUCCHresource set 1950, having a beam index indicating the RS1. The wirelessdevice 1920 may send, to the base station 1910, a PUCCH for a BFR usinga beam 1942, for example, if the wireless device 1920 selects a PUCCHresource, of the BFR PUCCH resource set 1950, having a beam indexindicating the RS2. The wireless device 1920 may send, to the basestation 1910, a PUCCH for a BFR using a beam 1943, for example, if thewireless device 1920 selects a PUCCH resource, of the BFR PUCCH resourceset 1950, having a beam index indicating the RS3.

The beam index of the PUCCH resource 1 may indicate the RS 1, the beamindex of PUCCH resource 2 may indicate the RS 2, and the beam index ofPUCCH resource 3 may indicate the RS 3, for example, if a beamcorrespondence exists. The downlink beam 1931 may correspond to theuplink beam 1941, the downlink beam 1932 may correspond to the uplinkbeam 1942, and the downlink beam 1933 may correspond to the uplink beam1943. The wireless device 1920 may trigger a PUCCH-based BFR procedure,for example, if the wireless device identifies a number of beam failureinstances on the first set of RSs (e.g., RS 0). The wireless device 1920may identify at least one RS (e.g., RS 2) from the second set of RSswhich has a quality (e.g., RSRP, RSRQ, BLER, etc.) satisfying (e.g.,better than or equal to) a configured threshold. To select the beam 1932as a candidate beam for a downlink transmission from the base station1910 to the wireless device 1920, the wireless device 1920 may determinethe PUCCH resource 2 associated with the RS 2. The wireless device 1920may determine the transmission beam 1942 based on the beam index, of thePUCCH resource 2, indicating RS 2. The wireless device 1920 may send(e.g., transmit) a PUCCH signal for a BFR on the transmission beam 1942via the PUCCH resource 2 (e.g., via the T_resource 2 and F_resource 2).The PUCCH signal for the BFR may be an SR signal, a beam request signal,or a beam report transmitted via the PUCCH resource 2 (e.g., via theT_resource 2 and F_resource 2). The base station 1910 may receive thePUCCH signal, via the PUCCH resource 2, by tuning (e.g., tuning areceiving antenna of the base station 1910) to a receiving beam (e.g.,the beam 1932) corresponding to the transmission beam (e.g., the beam1942 indicated by the beam index of the PUCCH resource 2). The basestation 1910 may determine (e.g., identify) that a BFR procedure istriggered by the wireless device 1920, for example, after or in responseto receiving the PUCCH signal for the BFR. The base station 1910 mayidentify: the candidate beam the wireless device 1920 selected based onthe PUCCH resource; the transmission beam of the PUCCH resource; and/orthe receiving beam of the base station 1910. The base station 1910 maydetermine that the candidate beam 1932 is a beam corresponding to RS2,for example, if the base station 1910 receives a PUCCH signal on thePUCCH resource 2 with the receiving beam 1932 corresponding to the beamindex associated with PUCCH resource 2. The base station 1910 may send(e.g., transmit) a PDCCH on a dedicated coreset to notify to thewireless device 1920 that the base station 1910 has received the PUCCHsignal. The wireless device 1920 may monitor a PDCCH on the dedicatedcoreset to receive the response of the base station 1910, for example,after the wireless device 1920 transmits the PUCCH signal. The BFRprocedure may be successfully completed, for example, after or inresponse to receiving the PDCCH. Based on the successful completion ofthe BFR procedure (e.g., including a successful reception of the PUCCHfor the BFR), the base station 1910 may select the candidate beam 1932(e.g., instead of the serving beam 1930) for sending a downlink signalto the wireless device 1920. A beam correspondence may exist, forexample, because the base station 1910 receives, via the beam 1932, thePUCCH for the BFR and selects the same beam 1932 to send the downlinksignal to the wireless device 1920.

A beam index of a PUCCH resource (e.g., the PUCCH resources 1, 2, or 3)may not necessarily indicate the RS index associated with a downlinkcandidate beam of the PUCCH resource, for example, if a beamcorrespondence does not exist. The base station 1910 may determine anuplink beam (e.g., a beam 1940 for an uplink transmission) has a goodsignal quality while a downlink beam (e.g., the beam 1930 for a downlinktransmission) fails (e.g., the wireless device 1920 fails to reliablyreceive the downlink signal sent by the transmission beam 1930). Thebeam indexes of the PUCCH resources 1, 2, and 3 may be configured toindicate the RS 0, for example, if the base station 1910 determines thatthe uplink beam (e.g., the beam 1940 for an uplink transmission and/orthe beam 1930 for an uplink reception) corresponding to the downlinkbeam (e.g., the beam 1940 for a downlink reception and/or the beam 1930for a downlink transmission associated with the RS 0) is good enough todetect a PUCCH signal from the wireless device 1920.

The beam index of PUCCH resource 1 may be configured to be a first RSindex, the beam index of PUCCH resource 2 may be configured to be asecond RS index, and the beam index of PUCCH resource 3 may beconfigured to be a third RS index. The first RS index may be an SSBindex, a CSI-RS index, or an SRS index. The second RS index may be anSSB index, a CSI-RS index, or an SRS index. The third RS index may be anSSB index, a CSI-RS index, or an SRS index. The first RS index, thesecond RS index, and the third RS index may be same or different, basedon implementation capability of the base station and/or the wirelessdevice. A base station and a wireless device may exchange informationrelated to at least one of: the wireless device's capability of beamcorrespondence; the base station's capability of beam correspondence;and/or a time duration in which a beam correspondence may exist if thebase station and the wireless device have the capability for supportingthe beam correspondence.

The wireless device 1920 may trigger a PUCCH-based BFR procedure, forexample, if the wireless device 1920 indicates a number of beam failureinstance on the first set of RSs (e.g., RS 0). The wireless device 1920may indicate at least one RS (e.g., RS 2) from the second set of RSswhich has a signal quality (e.g., RSRP, RSRQ, BLER, etc.) satisfying(e.g., better than) a configured threshold. The wireless device 1920 maydetermine a PUCCH resource (e.g., the PUCCH resource 2) associated withthe at least one identified RS (e.g., RS 2). The wireless device 1920may determine a transmission beam (e.g., the beam 1940) based on thebeam index (e.g., RS 0) of the PUCCH resource (e.g., the PUCCH resource2). The wireless device 1920 may send (e.g., transmit) a PUCCH signal onthe transmission beam 1940 via the PUCCH resource (e.g., the PUCCHresource 2). The PUCCH signal may be an SR signal, a beam requestsignal, and/or a beam report transmitted on the PUCCH resource. The basestation 1910 may receive the PUCCH signal by tuning to a receiving beam(e.g., the beam 1930 for an uplink reception) corresponding to thetransmission beam (e.g., the transmission beam 1940 indicated by the RS0 value of the beam index of the PUCCH resource 2) of the PUCCH resource(e.g., the PUCCH resource 2). The base station 1910 may determine (e.g.,identify) that the wireless device 1920 triggered a BFR procedure, forexample, after or in response to receiving the PUCCH signal. The basestation 1910 may determine the candidate beam 1932 the wireless device1920 selected (e.g., the wireless device 1902 implicitly selected thecandidate beam 1932 for a downlink transmission by selecting the PUCCHresource 2 associated with the RS 2). The base station 1910 maydetermine the candidate beam is the beam 1932 corresponding to RS2, forexample, if the base station 1910 receives a PUCCH signal on PUCCHresource 2 with the receiving beam 1930 corresponding to the beam index(e.g., RS 0) of the PUCCH resource 2. The base station 1910 may send(e.g., transmit) a PDCCH on a dedicated coreset to notify to thewireless device 1920 that the base station 1910 has received the PUCCHsignal. The wireless device 1920 may monitor the PDCCH on the dedicatedcoreset to receive the response of the base station 1910, for example,after the wireless device 1920 sent the PUCCH signal. The BFR proceduremay be successfully completed, for example, after or in response toreceiving the PDCCH.

The base station 1910 may flexibly indicate a transmission beam, of thewireless device 1920, for a PUCCH transmission used for a BFR procedure.The transmission beam of the PUCCH transmission may be indicated as abeam index value associated with a candidate beam (e.g., the RS 1 of thecandidate beam 1931). The transmission beam of the PUCCH transmissionmay be indicated as a beam index currently being used, for example, adownlink serving beam (e.g., the beam 1930) or an uplink SRStransmission beam (e.g., the beam 1940).

In a PUCCH configuration for a normal PUCCH transmission of an SR, or aHARQ-ACK, or a CSI report on a PUCCH, the base station 1910 may indicateat least one transmission beam for the normal PUCCH transmission. The atleast one transmission beam may comprise a beam index value (e.g., RS 0)associated with a serving beam (e.g., the beam 1930) and/or an uplinkSRS transmission beam (e.g., the beam 1940), instead of a beam indexassociated with a candidate beam. A beam from the at least onetransmission beam may be further activated by a MAC CE. The normal PUCCHresource set 1960 may comprise one or more normal PUCCH resources, whichmay not be resources for a BFR procedure. Each of the normal PUCCHresources may comprises different T_resource(s) and F_resource(s) (e.g.,PUCCH resource ‘a’ may comprise T_resource ‘a’ and F_resource ‘a’; andPUCCH resource ‘n’ may comprise T_resource ‘n’ and F_resource ‘n’). ThePUCCH resources (e.g., the PUCCH resource ‘a’ and the PUCCH resource‘n’) may comprise a beam index having the value (e.g., RS 0) associatedwith an active downlink beam (e.g., the active beam 1930) of the basestation 1910. The PUCCH resource ‘a’ may be used for an SR transmission.A PUCCH resource ‘b’ may be used for a CSI report. The PUCCH resource‘n’ may be used for a HARQ-ACK transmission. Based on the differentsettings for the beam index values, the base station 1910 and thewireless device 1920 may perform a PUCCH-based BFR procedure for boththe beam correspondence existence and/or the beam correspondencenon-existence.

FIG. 20 shows an example of configuring a PUCCH configuration for a BFRprocedure. One or more steps shown in FIG. 20 may be performed by awireless device (e.g., the wireless device 1920). At step 2001, thewireless device may receive one or more RRC messages configuring a BFRPUCCH resource set and at least one normal PUCCH resource set. At step2012, the wireless device may determine that an SR, a HARQ-ACK, and/or aCSI report is to be sent (e.g., transmitted) to a base station (e.g.,the base station 1910). At step 2013, the wireless device may select anormal PUCCH resource from the at least one normal PUCCH resource set.At step 2014, the wireless device may send (e.g., transmit) a PUCCHsignal via the normal PUCCH resource. Via an active beam (e.g., theactive beam 1940) of the wireless device, the wireless device may sendthe SR, the HARQ-ACK, and/or the CSI report. The selected normal PUCCHresource may comprise a beam index field indicating the active beam ofthe wireless device (e.g., the beam index field may have a valueindicating the RS 0 as shown in FIG. 19 ).

At step 2002, the wireless device may trigger a BFR procedure. The BFRprocedure may be triggered, for example, if there is a communicationquality problem with a downlink signal communication and/or an uplinksignal communication via active beams of the base station and thewireless device (e.g., the active beam 1930 of the base station 1910 andthe active beam 1940 of the wireless device 1920). At step 2003, thewireless device may select a BFR PUCCH resource from the BFR PUCCHresource set (e.g., the BFR PUCCH resource set 1950). At step 2004, thewireless device may send (e.g., transmit) a BFR signal via the BFR PUCCHresource. The selection of the BFR PUCCH resource (e.g., the PUCCHresource 2 of FIG. 19 ) may implicitly indicate, to the base station,that the wireless device has selected an associated candidate beam(e.g., the candidate beam 1932 associated with the RS 2 and associatedwith the PUCCH resource 2).

Multiple wireless devices may be located in a cell. Each wireless devicemay be allocated with multiple PUCCH resources for a BFR procedure, andeach PUCCH resource may be associated with a candidate beam. A basestation may reserve a large number of PUCCH resources for a BFRprocedure, which may not be efficient. Reserving a large number of PUCCHresources for a BFR procedure may result in inefficient radio resourceutilization. The PUCCH resource allocation efficiency for a BFRprocedure may be improved. To improve the PUCCH resource allocationefficiency for a BFR procedure, a dedicated PUCCH resource for a BFRprocedure for a wireless device may be used. The wireless device maysend (e.g., transmit), to a base station, a PUCCH signal comprising oneor more parameters indicating a candidate beam via the dedicated PUCCHresource. The dedicated PUCCH resource may be different from PUCCHresources for a normal PUCCH signal transmission (e.g., an SR, aHARQ-ACK, a CSI, and/or a beam report).

FIG. 21 shows an example of a PUCCH configuration for a BFR procedure. Abase station may send (e.g., transmit) at least one message comprisingparameters indicating a first set of RSs (e.g., one or more active setof RSs, such as RS 0) and a second set of RSs (e.g., one or morecandidate set of RSs, such as RS 1, RS 2 and RS 3). The at least onemessage may comprise an RRC message (e.g., an RRC connectionreconfiguration message, an RRC connection reestablishment message, anRRC connection setup message, etc.). The first set of RSs may identifyone or more active beams (e.g., a beam 2130) via which the base stationsends (e.g., transmits) a PDCCH and/or a PDSCH. The second set of RSsmay identify one or more candidate beams (e.g., beams 2131, 2132, and2133) from which the wireless device 2120 may select a candidate beamwith quality satisfying (e.g., better than) a threshold, for example, ifthe one or more beams (e.g., the beam 2130) associated with the firstset of RSs fail.

The at least one message may comprise parameters indicating a firstPUCCH resource for a BFR 2150 and at least one normal PUCCH resource set2160 comprising multiple PUCCH resources for normal PUCCH transmissions.The first PUCCH resource 2150 (e.g., a BFR PUCCH resource) may beidentified by at least one of: a first time resource (e.g., T_resource1); a first frequency resource (e.g., F_resource 1); a first cyclicshift of a base sequence; and/or a first beam index. Each of themultiple PUCCH resources for normal PUCCH transmissions may beidentified by at least one of: a second time resource (e.g., T_resourcen); a second frequency resource (e.g., F_resource n); a second cyclicshift of a base sequence; and/or a second beam index (e.g., indicatingthe RS 0).

The wireless device 2120 may send (e.g., transmit) a PUCCH signal viathe first PUCCH resource 2150, for example, if a BFR procedure istriggered. The PUCCH signal for the BFR may comprise at least oneparameter indicating at least one of: a beam failure; a candidate beam;and/or beam quality (e.g., RSRP) of the candidate beam.

The wireless device 2120 may determine a PUCCH resource from the normalPUCCH resource set, for example, if the wireless device 2120 performs anSR transmission (e.g., triggered by a BSR), a HARQ-ACK transmission, ora CSI report (e.g., a beam report) on a PUCCH. The first PUCCH resourcemay be different from the PUCCH resources of the normal PUCCH resourceset (e.g., at least one of: a time resource; a frequency resource; acyclic shift; an orthogonal code; and/or a beam index may be different).

The base station 2110 may set the first beam index for the first PUCCHresource to a serving beam index (e.g., RS 0 of the serving beam 2130),a candidate beam index (e.g., the RS 1, the RS 2, or the RS 3) otherthan the serving beam index, or a currently used uplink beam index(e.g., an SRS resource index), for example, for a beam correspondencenon-existence. The base station 2110 may set the first beam index forthe first PUCCH resource to a candidate beam index (e.g., the RS 1, theRS 2, or the RS 3), for example, for a beam correspondence existence.

The base station 2110 may set the first beam index to a predefined valueindicating the wireless device 2120 may determine a transmission beamcorresponding to a candidate beam, for example, for a beamcorrespondence existence. The wireless device 2120 may select, based onthe first beam index set to the predefined value, both the candidatebeam of the base station 2110 and the transmission beam, of the wirelessdevice 2120, for a PUCCH transmission for a BFR. The wireless device2120 may determine the transmission beam (e.g., the beam 2142)corresponding to a receiving beam (e.g., the beam 2132 for the RS 2),for example, if the wireless device 2120 selects the RS 2 as thecandidate beam. The wireless device 2120 may send (e.g., transmit) aPUCCH signal via the transmission beam. The PUCCH signal may comprise atleast one parameter indicating at least one of: a beam failureoccurrence; a beam indicator; and/or beam quality of the candidate beam.

The base station 2110 may detect the PUCCH signal sent via the firstPUCCH resource by using a receiving beam (e.g., the beam 2132)corresponding to the beam index (e.g., the RS 2) of the first PUCCHresource. The base station 2110 may decode the received PUCCH signal toretrieve information of the PUCCH signal (e.g., a beam indicator and/orbeam quality of the candidate beam). The base station 2110 may send(e.g., transmit) a PDCCH on a coreset (e.g., a dedicated coreset for aBFR procedure) to the wireless device 2120. The wireless device 2120 maymonitor the PDCCH for detecting downlink control information, forexample, after or in response to sending (e.g., transmitting) the PUCCHsignal via the first PUCCH resource. The PDCCH may be sent via thecandidate beam, of the base station 2110, selected by the wirelessdevice 2120. The wireless device 2120 may complete the PUCCH-based BFRprocedure, for example, after or in response to detecting the downlinkcontrol information on the coreset.

FIG. 22 shows an example of configuring a PUCCH configuration for a BFRprocedure. One or more steps shown in FIG. 22 may be performed by awireless device (e.g., the wireless device 2120). At step 2201, thewireless device may receive one or more RRC messages configuring a BFRPUCCH resource and at least one normal PUCCH resource set. At step 2212,the wireless device may determine that an SR, a HARQ-ACK, and/or a CSIreport is to be sent (e.g., transmitted) to a base station (e.g., thebase station 2110). At step 2213, the wireless device may select anormal PUCCH resource from the at least one normal PUCCH resource set.At step 2214, the wireless device may send (e.g., transmit) a PUCCHsignal via the normal PUCCH resource. Via an active beam (e.g., theactive beam 2140) of the wireless device, the wireless device may sendthe SR, the HARQ-ACK, and/or the CSI report. The selected normal PUCCHresource may comprise a beam index field indicating the active beam ofthe wireless device (e.g., the beam index field may have a valueindicating the RS 0 as shown in FIG. 21 ).

At step 2202, the wireless device may trigger a BFR procedure. The BFRprocedure may be triggered, for example, if there is a communicationquality problem with a downlink signal communication and/or an uplinksignal communication via active beams of the base station and wirelessdevice (e.g., the active beam 2130 of the base station 2110 and theactive beam 2140 of the wireless device 2120). At step 2203, thewireless device may select a BFR PUCCH resource (e.g., the first PUCCHresource for the BFR 2150) and may generate a BFR signal comprising abeam indicator (e.g., one of beam indicators shown in FIG. 23 ). At step2204, the wireless device may send (e.g., transmit) the generated BFRsignal via the BFR PUCCH resource.

The beam index of the second set of RSs indicated in the at least onemessage may be a SSB resource index/ID or a CSI-RS resource index/ID(e.g., at most 64). The number of RSs in the second set of RSs may be anumber no more than 4, or 8, or 16, depending on a configuration of abase station (e.g., the base stations 1910 and 2110, etc.). It may benecessary to map a beam index associated with an RS index/ID (e.g., atmost 64) from the second set of RSs to a beam indicator (e.g., 2 bits, 3bits or 4 bits) used in a PUCCH signal transmission. The beam indicatormay be 2 bits, for example, the number of RSs in the second set of RSsis 4 or less. The beam indicator may be 3 bits, for example, the numberof RSs in the second set of RSs is more than 4 and less than 9. The beamindicator may be 4 bits, for example, the number of RSs in the secondset of RSs is more than 8 and less than 17. The base station 2110 may(e.g., explicitly) indicate, to the wireless device 2120 and via the atleast one message, the size (e.g., the bit width) of the beam indicatordetermined based on the number of second set of RSs. By indicating thenumber of second set of RSs, the base station 2110 may implicitlyindicate, to the wireless device 2120, the size (e.g., the bit width) ofthe beam indicator.

FIG. 23 shows an example beam index mapping procedure. The mappingbetween a bit value of a beam indicator and a beam index (e.g., the SSBresource index/ID or a CSI-RS resource index/ID) of the second set ofRSs may be predefined or preconfigured. 4 RSs (RS 12, RS 21, RS 54, andRS 62) may be comprised in the second set of RSs. The first beam index(e.g., RS 12) may be represented by a 2-bit beam indicator (e.g., “00”),the second beam index (e.g., RS 21) may be represented by “01”, thethird beam index (e.g., RS 54) may be represented by “10”, and thefourth beam index (e.g., RS 62) may be represented by “11”. A basestation and one or more wireless devices may presume that a lower beamindex is mapped to a lower bit value of a beam indicator and that ahigher beam index is mapped to a higher bit value of a beam indicator(e.g., as shown in FIG. 23 ). A wireless device may set the beamindicator to “01” in the PUCCH signal, for example, if the wirelessdevice selects a beam corresponding to the RS 21 as a candidate beam.The base station may determine the candidate beam associated with thebeam index RS 21 as the candidate beam selected by the wireless device,for example, if the base station receives the PUCCH signal anddetermines that the beam indicator contained in the PUCCH signal is“01”. The example mapping may reduce the bit number used in a PUCCHsignal to indicate a candidate beam index, and may improve the PUCCHtransmission robustness and/or efficiency.

The number of RSs in the second set of RSs may be more than 4 and nomore than 8 (e.g., the second set of RSs may have 5 RSs, 6 RSs, 7 RSs,or 8 RSs). The first beam index in the second set of RSs may be mappedto a first 3-bit beam indicator “000”, the second beam index mapped to asecond 3-bit beam indicator “001”, . . . , and the eighth beam index ofthe second set of RSs may be mapped to an eighth 3-bit beam indicator“111”, for example, according to ascending order. A wireless device mayset the beam indicator to “000” in the PUCCH signal, for example, if thewireless device selects a beam corresponding to the first beam index.The mapping in ascending order may apply between different 4-bit beamindicators and different RSs in the second set of RSs, for example, ifthe number of RSs in the second set of RSs is more than 8 and no morethan 16. The bit number used in beam indicator of PUCCH signal may belog 2K, for example, if the number of the second set of RSs is K. Thefirst beam index of the second set of RSs may be represented by anall-zero bit string with a length of log 2K bits. The last beam index ofthe second set of RSs may be represented by an all-one bit string with alength of log 2K bits.

A wireless device may receive, from a base station, at least one messagecomprising first configuration parameters of one or more first PUCCHresources and comprising second configuration parameters of one or moresecond PUCCH resources. Each of the one or more first PUCCH resourcesmay be identified by first parameters comprising at least one RS indexof the PUCCH resource(s) for a BFR (e.g., RS 0, RS 1, RS 2, RS 3, etc.).Each of the one or more second PUCCH resources may be identified bysecond parameters comprising at least one RS index of a PUCCH resourcefor a normal PUCCH (e.g., RS 0). The wireless device may select a firstPUCCH resource from one or more first PUCCH resources for a BFR, forexample, if a BFR procedure is initiated. The wireless device maydetermine a first transmission beam based on the at least one RS indexof the first PUCCH resource. The wireless device may send (e.g.,transmit) at least one first uplink signal via the first transmissionbeam and via the first PUCCH resource. The wireless device may select asecond PUCCH resource from one or more second PUCCH resources of anormal PUCCH resource set, for example, if a PUCCH transmission for anSR, a HARQ-ACK, or a CSI report is triggered. The wireless device maydetermine a second transmission beam based on the at least one RS indexof the second PUCCH resource. The wireless device may send (e.g.,transmit) at least one second uplink signal via the second transmissionbeam and via the second PUCCH resource.

The at least one message may comprise one or more first RS resources(e.g., RS 0) for the normal PUCCH resource set and/or comprise one ormore second RS resources for the one or more first PUCCH resources for aBFR. Each of the one or more second RS resources may be associated withone or more first PUCCH resources. A first RS of the one or more secondRS resources may be associated with a first PUCCH resource of the one ormore first PUCCH resources. A second RS of the one or more second RSresources may be associated with a second PUCCH resource of the one ormore first PUCCH resources.

The beam failure recovery procedure being initiated may comprise atleast one of: measuring at least one downlink control channel withsignal strength not satisfying (e.g., lower than) a first threshold;and/or selecting a candidate RS, in the one or more second RSs, based ona second threshold.

The wireless device may determine the first PUCCH resource associatedwith the selected RS. Each of the one or more first PUCCH resources maycomprise at least one of: a cyclic shift; a time resource; a frequencyresource; and/or an orthogonal cover code. The at least one first uplinksignal may be a scheduling request.

FIG. 24 shows an example of configuring a beam indicator associated witha beam index. One or more steps shown in FIG. 24 may be performed by awireless device (e.g., the wireless device 2120). At step 2401, thewireless device may determine a candidate beam of a base station (e.g.,the beam 2132 of the base station 2110). The wireless device maydetermine the candidate beam by selecting an RS from the second set ofRSs (e.g., RS 1, RS 2, and RS 3) configured by an RRC message. Thewireless device may determine the candidate beam, for example, for a BFRprocedure. A downlink signal sent from the serving beam 2130 of the basestation 2110 may have a low quality for the wireless device 2120, andthe wireless device 2120 may determine one or more beam failureinstances. The wireless devices 2120 may measure reference signals ofthe candidate beams 2131, 2132, and 2133. The candidate beam 2131 maysend the RS 1, the candidate beam 2132 may send the RS 2, and thecandidate beam may send the RS 3. The wireless device 2120 may selectthe RS 2 (and the candidate beam 2132), for example, if the signalquality of the RS 2 satisfies one or more threshold (e.g., the RSRP ofthe RS 2 is greater than a threshold). At step 2402, the wireless devicemay determine a beam indicator associated with the selected candidatebeam. The beam indicator may have a 2-bit value, for example, if thenumber of candidate beams of the base station configurable for thewireless device is less than or equal to four (e.g., three candidatebeams 2131, 2132, and 2133 of the base station 2110 may be configurablefor the wireless device 2120 in FIG. 21 ). A beam indicator value ‘00’may indicate the candidate beam 2131, a beam indicator ‘01’ may indicatethe candidate beam 2132, and the beam indicator ‘10’ may indicate thecandidate beam 2133. The beam indicator may have a 3-bit value, forexample, if the number of candidate beams of the base stationconfigurable for the wireless device is less than or equal to eight. Thebeam indicator may have a 4-bit value, for example, if the number ofcandidate beams of the base station configurable for the wireless deviceis less than or equal to sixteen. At step 2403, the wireless device maysend (e.g., transmit), to the base station, a PUCCH signal comprisingthe selected beam indicator. The base station may select, afterreceiving the PUCCH signal and based on the value of the selected beamindicator, one of the candidate beams of the base station for a BFR. Thebase station may send, after receiving the PUCCH signal comprising theselected beam indicator, a downlink control signal by using the selectedcandidate beam of the base station.

FIG. 25 shows an example of a beam selection for a BFR procedure. A basestation 2510 may send, to a wireless device 2520, one or more messages(e.g., one or more RRC messages). The wireless device 2520 may receivethe one or more messages via an active beam 2541 of the wireless device2520. The one or more messages may comprise one or more RRCconfiguration parameters for a BFR. The one or more messages may be sentvia a serving beam (e.g., an active beam) 2531. The one or more RRCconfiguration parameters for the BFR may comprise a set of RSsindicating a plurality of candidate beams 2530 and 2532 that may be usedfor the wireless device 2520. A first candidate beam 2530 of the basestation 2510 may be associated with a first RS (e.g., RS 0), and asecond candidate beam 2532 of the base station 2510 may be associatedwith a second RS (e.g., RS 2). The serving beam 2531 of the base station2510 may be associated with a third RS (e.g., RS 1). The one or more RRCconfiguration parameters for the BFR may comprise one or more beamindexes (e.g., the beam indexes of the BFR PUCCH resource set 1950, thebeam index of the first PUCCH resource for BFR 2150, etc.) to indicate acandidate beam of the wireless device 2520 for the BFR.

The one or more messages may comprise at least one normal PUCCH resourceset (e.g., the normal PUCCH resource set 1960, the normal PUCCH resourceset 2160, etc.). The at least one normal PUCCH resource set may compriseone or more normal PUCCH resources. The one or more normal PUCCHresources may comprise a beam index indicating the third RS associatedwith the serving beam 2531. The wireless device 2520 may send, to thebase station 2510 and via the active beam 2541, an uplink signal (e.g.,an SR, a HARQ-ACK, and/or a CSI report). The sending of the uplinksignal may be based on the one or more normal PUCCH resources.

The wireless device 2520 may determine a BFR by detecting one or morebeam failure instances. The wireless device 2520 may measure a downlinksignal sent from the serving beam 2531 and received by the active beam2541. The downlink signal may comprise the third RS (e.g., RS 1), andthe wireless device may measure the signal quality (e.g., RSRP) of thethird RS. The wireless device 2520 may detect one or more beam failureinstances by determining a failure of decoding the downlink signal,determining the signal quality of the third RS does not satisfy one ormore thresholds (e.g., the signal quality is lower than a threshold),etc.

The wireless device 2520 may measure downlink signals sent from thecandidate beams 2530 and 2532. The wireless device 2520 may receive, viaa candidate beam 2540 of the wireless device 2520, the first RS sentfrom the candidate beam 2530, and may receive, via a candidate beam 2542of the wireless device 2520, the second RS sent from the candidate beam2532. The wireless device 2520 may determine, based on the measurements,that the signal quality of the second RS is better than the signalquality of the first RS, and may select the candidate beam 2532 for theBFR. To indicate the selection of the candidate beam 2532, the wirelessdevice 2520 may trigger an uplink transmission (e.g., a PUCCHtransmission, an SR transmission, etc.) for the BFR.

The wireless device 2520 may send, via a candidate beam 2542, the uplinktransmission for the BFR. The candidate beam 2542 may be indicated bythe one or more beam indexes (e.g., the beam indexes of the BFR PUCCHresource set 1950, the beam index of the first PUCCH resource for BFR2150, etc.) sent from the base station 2510. The base station 2510 mayreceive, via the beam 2532 of the base station 2510 associated with thecandidate beam 2542, the uplink transmission for the BFR. The basestation 2510 may determine, based on the one or more beam indexes set bythe base station 2510, the beam 2532 of the base station 2510 associatedwith the candidate beam 2542. The base station 2510 may retrieve a beamindicator from the received uplink transmission for the BFR, and maydetermine, based on the beam indicator, the candidate beam 2532 selectedby the wireless device 2520 for a response to the uplink transmissionfor the BFR. The base station 2510 may send, via the candidate beam2532, the response to complete the BFR for the wireless device 2520.Although FIG. 25 shows that the base station 2510 receives the uplinktransmission for the BFR via the candidate beam 2532 and sends theresponse via the candidate beam 2532, the receiving beam and thetransmission beam of the base station 2510 may be different. Forexample, the base station 2510 may set the one or more beam indexesdifferently, and the wireless device may send, via the candidate beam2540, the uplink transmission for the BFR. The base station 2510 mayreceive, via the candidate beam 2530, the uplink transmission for theBFR. The base station 2510 may determine the candidate beam 2532 for thetransmission of the response, for example, if the uplink transmissionfor the BFR comprises a beam indicator associated with the candidatebeam 2532 or if the uplink transmission for the BFR has been sent via aBFR PUCCH resource associated with the candidate beam 2532.

FIG. 26 shows an example of performing a BFR procedure. One or moresteps shown in FIG. 26 may be performed by a base station (e.g., thebase station 1910, 2110, and 2510). At step 2601, the base station mayestablish an RRC connection with a wireless device (e.g., the wirelessdevice 1920, 2120, and 2520), and may generate one or more messages forthe wireless device. The one or more messages may comprise one or moreRRC messages and may be the one or more messages discussed above (e.g.,the one or more messages discussed with respect to FIGS. 19-25 ). To setone or more configuration parameters of the one or more messages, thebase station may determine the number of the first set of RSs (e.g., oneor more active set of RSs, such as the RS 0 of a serving beam) and thenumber of the second set of RSs (e.g., one or more candidate set of RSs,such as the RS 1, the RS 2, and the RS 3 of candidate beams). The basestation may configure normal PUCCH resources for the wireless device andconfigure one or more BFR PUCCH resources for the wireless device. Thenumber of BFR PUCCH resources may be based on the number of the secondset of RSs (e.g., as shown in FIG. 19 ) or may be less than the numberof the second set of RSs (e.g., as shown in FIG. 21 ). The base stationmay set a beam index as a configuration parameter. Each of the BFR PUCCHresources may comprise a beam index (e.g., as shown in FIG. 19 ).Similar to the RS signal measurements by the wireless device, the basestation may measure RS signals transmitted from a plurality oftransmission beams of the wireless device. Based on the measurements bythe base station, the base station may select one or more candidatebeams of the wireless device. The base station may determine the one ormore beam indexes based on the selected candidate beam(s) of thewireless device. The base station may determine RS 2 as a value of thebeam index of the first PUCCH resource for the BFR 2150, for example, ifthe base station determines that the signal received from thetransmission beam 2142 has the best signal quality among the candidatebeams 2141, 2142, and 2143. The base station may determine RS 1 asvalues of the beam indexes of the BFR PUCCH resource set 1950, forexample, if the base station determines that the signal received fromthe transmission beam 1941 has the best signal quality among thecandidate beams 1941, 1942, and 1943. The base station may set differentbeam indexes for different BFR PUCCH resources. The base station maydetermine RS 1 as values of the beam indexes of the PUCCH resource 1 andthe PUCCH resource 3, and may determine RS 2 as a value of the beamindex of the PUCCH resource 2.

At step 2602, the base station may monitor an uplink signaltransmission, of the wireless device, for the BFR. The base station maymonitor the uplink signal transmission based on the beam index(s). Thebase station may monitor an uplink signal (e.g., RS 2) sent from thebeam 2142 and may receive, via the beam 2132, the uplink signal, forexample, if the beam index of the first PUCCH resource for the BFRindicates the RS 2. The base station may monitor an uplink signal (e.g.,RS 1) sent from the beam 1941, for example, if the beam indexes of theBFR PUCCH resource set 1950 indicate the RS 1. The base station mayassume that the uplink signal may be sent via one of the PUCCH resource1, the PUCCH resource 2, or the PUCCH resource 3. The base station maymonitor a first uplink signal (e.g., RS 1) sent from the beam 1941 andmay monitor a second uplink signal (e.g., RS 2) sent from the beam 1942,for example, if the beam indexes of the PUCCH resource 1 and the PUCCHresource 3 indicate the RS 1 and if the beam index of the PUCCH resource2 indicates the RS 2. The base station may assume that the first uplinksignal may be sent via one of the PUCCH resource 1 or the PUCCH resource3 and may assume that the second uplink signal may be sent via the PUCCHresource 2.

At step 2603, the base station may determine, based on the receiveduplink signal(s), one or more candidate beams of the base station. Thebase station may retrieve a beam indicator from the received uplinksignal, for example, if the wireless device sends an uplink signalcomprising one of the beam indicators (e.g., as shown in FIG. 23 ). Thebase station may receive one or more uplink signals mapped on one ormore of BFR PUCCH resources (e.g., the PUCCH resource 1, the PUCCHresource 2, and the PUCCH resource 3 shown in FIG. 19 ). The basestation (e.g., the base station 1910) may select the candidate beams1932 and 1933, for example, if the wireless device 1920 sends, via thePUCCH resource 2 and the PUCCH resource 3, uplink signals for the BFR.If the base station 1910 and the wireless device 1920 use more than oneBFR PUCCH resource of the BFR PUCCH resource set 1950, the successprobability of the BFR procedure may increase.

A base station may send, to a wireless device, one or more configurationparameters associated with a BFR procedure. The one or moreconfiguration parameters may comprise a plurality of RS resources andcomprise an RS resource index associated with an uplink control channel(e.g., a PUCCH channel). The one or more configuration parameters maycomprise configuration parameters of a PUCCH for the BFR procedure. Thewireless device may determine (e.g., select), from the plurality of RSresources, a first RS resource. The wireless device may identify, basedon initiating the BFR procedure, the first RS resource. The wirelessdevice may determine, based on one or more thresholds and based oninitiating the BFR procedure, the first RS resource. The first RSresource may be associated with a candidate beam of the base station.The configuration parameters may comprise the plurality of RS resourceseach associated with a different candidate beam of the base station. Thewireless device may determine, based on the RS resource index (e.g., theRS resource index being set to a first value), one or more transmissionbeam parameters (e.g., a spatial filter) for the uplink control channel.The wireless device may transmitting, based on the one or moretransmission beam parameters and via the uplink control channel, uplinkcontrol information for the BFR procedure and to indicate the first RSresource. The wireless device may initiate, based on one or more beamfailures, the BFR procedure. The wireless device may determine, based onthe RS resource index, a beam of the wireless device. The wirelessdevice may transmit, based on the beam of the wireless device, theuplink control information for the BFR procedure. The uplink controlinformation may comprise at least one of: information indicating thefirst RS resource or an RSRP value of the first RS resource. The uplinkcontrol information for the BFR procedure may comprise a beam indicatorindicating the first RS resource. The selection of the uplink controlchannel may indicate the first RS resource. The one or moreconfiguration parameters may indicate a plurality of uplink controlchannel resources each associated with a different RS resource of theplurality of RS resources. A first uplink control channel resource, ofthe plurality of uplink control channel resources may be associated withthe uplink control channel and may comprise the RS resource index. Aselection of the first uplink channel resource may indicate, to the basestation, at least one of: the first RS resource or a first candidatebeam of the base station. The wireless device may select, from theplurality of control channel resources and based on the first RSresource, a first uplink control channel resource. The wireless devicemay determine, based on the first uplink control channel resource, theuplink control channel. The first RS resource may comprise at least oneof: one or more channel state information RS resources or one or moresynchronization signal blocks. The RS resource index may indicate atleast one of: one or more channel state information RS resources, one ormore synchronization signal blocks, or one or more sounding referencesignal resources. The RS resource index associated with the uplinkcontrol channel may indicate a candidate transmission beam of thewireless device. The RS resource index may indicate one or moretransmission beam parameters of the candidate transmission beam of thewireless device. The uplink control channel may be associated with thefirst RS. The wireless device may select, based on the first RSresource, the uplink control channel from a plurality of uplinkchannels. The wireless device may transmit a capability indicationmessage (e.g., a capability response message) comprising a firstcapability parameter indicating whether a beam correspondence issupported. The capability indication message may indicate that a beamcorrespondence is not supported. The uplink control information or theuplink control channel indicates a selection of the candidate beam ofthe base station. The wireless device may receive, based on the firstcapability parameter indicating a beam correspondence is not supported,the configuration parameters. The wireless device may select the firstRS resource, for example, based on channel quality of the first RSresource satisfying (e.g., greater than) the one or more thresholds. Thewireless device may initiate the BFR procedure, for example, based ondetecting a number of beam failure instances. The wireless device maydetect the number of beam failure instances, for example, based onchannel quality of one or more second RS resources and one or morethresholds. The one or more second RS resources may be associated withone or more serving beams of the base station. The channel quality ofthe one or more second RS resources may comprise at least one of: avalue of RSRP, a value of channel quality indicator, or a block errorrate. The one or more thresholds may be comprised in the configurationparameters. The one or more second RS resources may comprise one or morechannel state information RS resources or one or more synchronizationsignal blocks. The wireless device may detect the number of beam failureinstances, for example, based on the channel quality of the one or moresecond RS resources not satisfying (e.g., lower than) the one or morethresholds. The wireless device may monitor a downlink control channelfor a response to the uplink control information, for example, after orin response to transmitting the uplink control information. The wirelessdevice may receive, during monitoring the downlink control channel, theresponse via the downlink control channel. The wireless device maycomplete the BFR procedure, for example, based on receiving theresponse. The wireless device may transmit second uplink controlinformation via a second uplink control channel, for example, after orin response to not receiving the response during the monitoring. Thewireless device may increment a BFR request transmission counter, forexample, after transmitting the second uplink control information. Thewireless device may monitor a second downlink control channel for asecond response to the second uplink control information. The wirelessdevice may complete the BFR procedure, for example, after or in responseto not receiving the second response during monitoring the seconddownlink control channel and the BFR request transmission countersatisfying (e.g., equal to or greater than) a first value (e.g., amaximum BFR transmission counter value).

FIG. 27 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 2700 may include one ormore processors 2701, which may execute instructions stored in therandom access memory (RAM) XX03, the removable media 2704 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive2705. The computing device 2700 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 2701 andany process that requests access to any hardware and/or softwarecomponents of the computing device 2700 (e.g., ROM 2702, RAM 2703, theremovable media 2704, the hard drive 2705, the device controller 2707, anetwork interface 2709, a GPS 2711, a Bluetooth interface 2712, a WiFiinterface 2713, etc.). The computing device 2700 may include one or moreoutput devices, such as the display 2706 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 2707, such as a video processor. There mayalso be one or more user input devices 2708, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device2700 may also include one or more network interfaces, such as a networkinterface 2709, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 2709 may provide aninterface for the computing device 2700 to communicate with a network2710 (e.g., a RAN, or any other network). The network interface 2709 mayinclude a modem (e.g., a cable modem), and the external network 2710 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 2700 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 2711, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 2700.

The example in FIG. 27 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 2700 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 2701, ROM storage 2702, display 2706, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 27 .Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

1. A method comprising: receiving, by a wireless device, one or moreconfiguration parameters associated with beam failure recovery, whereinthe one or more configuration parameters indicate: one or more candidatereference signals (RSs) associated with downlink reception; and areference signal (RS) resource index associated with uplinktransmission; and transmitting, based on beam failure recoveryassociated with the one or more candidate RSs and using one or moretransmission beam parameters associated with the RS resource index,uplink information for beam failure recovery.
 2. The method of claim 1,wherein: each candidate RS of the one or more candidate RSs isassociated with a candidate beam of a base station; the one or moretransmission beam parameters is associated with a transmission beam ofthe wireless device; and the transmitting the uplink information forbeam failure recovery is based on the transmission beam of the wirelessdevice.
 3. The method of claim 1, wherein the RS resource indexassociated with uplink transmission indicates at least one of: a channelstate information RS resource; a synchronization signal block resource;or a sounding reference signal resource.
 4. The method of claim 1,further comprising transmitting, for beam failure recovery, anindication of a first candidate RS of the one or more candidate RSs. 5.The method of claim 1, further comprising transmitting, by the wirelessdevice, a capability indication message indicating whether the wirelessdevice supports beam correspondence.
 6. The method of claim 1, furthercomprising: determining, from the one or more candidate RSs, a firstcandidate RS for beam failure recovery; and determining, for thetransmitting the uplink information for beam failure recovery and basedon the RS resource index associated with uplink transmission, the one ormore transmission beam parameters.
 7. The method of claim 1, furthercomprising: selecting, based on beam failure recovery being associatedwith a secondary cell, a physical uplink control channel (PUCCH) for thetransmitting the uplink information for beam failure recovery, whereinthe secondary cell is different from a primary cell.
 8. The method ofclaim 1, wherein the one or more configuration parameters compriseconfiguration parameters for physical uplink control channel (PUCCH)transmission, and wherein the uplink information is a scheduling requestfor beam failure recovery.
 9. The method of claim 1, wherein the one ormore configuration parameters comprise configuration parameters forphysical uplink control channel (PUCCH) transmission, and wherein theuplink information is uplink control information for beam failurerecovery.
 10. A method comprising: transmitting, by a base station, oneor more configuration parameters associated with beam failure recovery,wherein the one or more configuration parameters indicate: one or morecandidate reference signals (RSs) associated with downlink transmission;and a reference signal (RS) resource index associated with uplinkreception; and receiving, based on beam failure recovery associated withthe one or more candidate RSs and using one or more reception beamparameters associated with the RS resource index, uplink information forbeam failure recovery.
 11. The method of claim 10, wherein: eachcandidate RS of the one or more candidate RSs is associated with acandidate beam of the base station; the one or more reception beamparameters is associated with a reception beam of the base station thatis associated with a transmission beam of a wireless device; and thereceiving the uplink information for beam failure recovery is based onthe reception beam of the base station.
 12. The method of claim 10,wherein the RS resource index associated with uplink reception indicatesat least one of: a channel state information RS resource; asynchronization signal block resource; or a sounding reference signalresource.
 13. The method of claim 10, further comprising receiving, forbeam failure recovery, an indication of a first candidate RS of the oneor more candidate RSs.
 14. The method of claim 10, further comprisingreceiving, from a wireless device, a capability indication messageindicating whether the wireless device supports beam correspondence. 15.The method of claim 10, further comprising: determining, for receptionof uplink information for beam failure recovery and based on the RSresource index associated with uplink reception, the one or morereception beam parameters.
 16. The method of claim 10, furthercomprising: determining, after reception of an indication of a firstcandidate RS of the one or more candidate RSs, a beam failure associatedwith a secondary cell; and transmitting, via a beam associated with thefirst candidate RS, downlink information.
 17. The method of claim 10,wherein the one or more configuration parameters comprise configurationparameters for physical uplink control channel (PUCCH) transmission, andwherein the uplink information is a scheduling request for beam failurerecovery.
 18. The method of claim 10, wherein the one or moreconfiguration parameters comprise configuration parameters for physicaluplink control channel (PUCCH) transmission, and wherein the uplinkinformation is uplink control information for beam failure recovery. 19.A wireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors,configure the wireless device to: receive one or more configurationparameters associated with beam failure recovery, wherein the one ormore configuration parameters indicate: one or more candidate referencesignals (RSs) associated with downlink reception; and a reference signal(RS) resource index associated with uplink transmission; and transmit,based on beam failure recovery associated with the one or more candidateRSs and using one or more transmission beam parameters associated withthe RS resource index, uplink information for beam failure recovery. 20.The wireless device of claim 19, wherein: each candidate RS of the oneor more candidate RSs is associated with a candidate beam of a basestation; the one or more transmission beam parameters is associated witha transmission beam of the wireless device; and the instructions, whenexecuted by the one or more processors, configure the wireless device totransmit the uplink information for beam failure recovery based on thetransmission beam of the wireless device.
 21. The wireless device ofclaim 19, wherein the RS resource index associated with uplinktransmission indicates at least one of: a channel state information RSresource; a synchronization signal block resource; or a soundingreference signal resource.
 22. The wireless device of claim 19, whereinthe instructions, when executed by the one or more processors, furtherconfigure the wireless device to transmit, for beam failure recovery, anindication of a first candidate RS of the one or more candidate RSs. 23.The wireless device of claim 19, wherein the instructions, when executedby the one or more processors, further configure the wireless device totransmit a capability indication message indicating whether the wirelessdevice supports beam correspondence.
 24. The wireless device of claim19, wherein the instructions, when executed by the one or moreprocessors, further configure the wireless device to: determine, fromthe one or more candidate RSs, a first candidate RS for beam failurerecovery; and determine, for transmitting the uplink information forbeam failure recovery and based on the RS resource index associated withuplink transmission, the one or more transmission beam parameters. 25.The wireless device of claim 19, wherein the instructions, when executedby the one or more processors, further configure the wireless device to:select, based on beam failure recovery being associated with a secondarycell, a physical uplink control channel (PUCCH) for transmitting theuplink information for beam failure recovery, wherein the secondary cellis different from a primary cell.
 26. The wireless device of claim 19,wherein the one or more configuration parameters comprise configurationparameters for physical uplink control channel (PUCCH) transmission, andwherein the uplink information is a scheduling request for beam failurerecovery.
 27. The wireless device of claim 19, wherein the one or moreconfiguration parameters comprise configuration parameters for physicaluplink control channel (PUCCH) transmission, and wherein the uplinkinformation is uplink control information for beam failure recovery. 28.A base station comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors,configure the base station to: transmit one or more configurationparameters associated with beam failure recovery, wherein the one ormore configuration parameters indicate: one or more candidate referencesignals (RS s) associated with downlink transmission; and a referencesignal (RS) resource index associated with uplink reception; andreceive, based on beam failure recovery associated with the one or morecandidate RSs and using one or more reception beam parameters associatedwith the RS resource index, uplink information for beam failurerecovery.
 29. The base station of claim 28, wherein: each candidate RSof the one or more candidate RSs is associated with a candidate beam ofthe base station; the one or more reception beam parameters isassociated with a reception beam of the base station that is associatedwith a transmission beam of a wireless device; and the instructions,when executed by the one or more processors, configure the base stationto receive the uplink information for beam failure recovery based on thereception beam of the base station.
 30. The base station of claim 28,wherein the RS resource index associated with uplink reception indicatesat least one of: a channel state information RS resource; asynchronization signal block resource; or a sounding reference signalresource.
 31. The base station of claim 28, wherein the instructions,when executed by the one or more processors, further configure the basestation to receive, for beam failure recovery, an indication of a firstcandidate RS of the one or more candidate RSs.
 32. The base station ofclaim 28, wherein the instructions, when executed by the one or moreprocessors, further configure the base station to receive, from awireless device, a capability indication message indicating whether thewireless device supports beam correspondence.
 33. The base station ofclaim 28, wherein the instructions, when executed by the one or moreprocessors, further configure the base station to: determine, forreception of uplink information for beam failure recovery and based onthe RS resource index associated with uplink reception, the one or morereception beam parameters.
 34. The base station of claim 28, wherein theinstructions, when executed by the one or more processors, furtherconfigure the base station to: determine, after reception of anindication of a first candidate RS of the one or more candidate RSs, abeam failure associated with a secondary cell; and transmit, via a beamassociated with the first candidate RS, downlink information.
 35. Thebase station of claim 28, wherein the one or more configurationparameters comprise configuration parameters for physical uplink controlchannel (PUCCH) transmission, and wherein the uplink information is ascheduling request for beam failure recovery.
 36. The base station ofclaim 28, wherein the one or more configuration parameters compriseconfiguration parameters for physical uplink control channel (PUCCH)transmission, and wherein the uplink information is uplink controlinformation for beam failure recovery.